Megaware 1

home *** CD-ROM | disk | FTP | other *** search

/ Megaware 1 / Megaware Volume 1.iso / utils / mem-expa / technote.doc < prev next >

Wrap

Text File | 1988-12-15 | 21.0 KB | 561 lines

V-EMM COMPATIBILITY GUIDE ------------------------- Release 2.06 of V-EMM, the Virtual Expanded Memory Manager. Copyright (C) Rocke Verser, 1986, 1988. All rights reserved. Fort's Software Fort's Software P. O. Box 1295 P. O. Box 396 Loveland, Colorado 80539 Manhattan, Kansas 66502 (303) 663-5629 (913) 537-2897 PREFACE ------- In general, most Application Software runs fine under V-EMM. Where a problem exists, it can usually be found in Operating Environments or in Utility Software. Problems usually occur only when V-EMM is running with certain drivers or options. This file lists known and potential compatibility problems between V-EMM and various commercially available software. This file is divided into two major sections. The first sec- tion lists a number of commercial products, and their compat- ibility with V-EMM. The second section gives a technical overview of the possible sources of incompatibility. COMPATIBILITY WITH COMMERCIAL SOFTWARE -------------------------------------- V-EMM is compatible with the vast majority of EMS applications. Following, we list a representative sample of the most popular products with which V-EMM has been tested. We have also listed known incompatibilities with popular products. And we have attempted to offer some tips on setting up your software to work well with V-EMM. Some of this information comes from our own technical support department; some of this information comes from vendors of these products; and some of this information comes from customers who have reported success or failure in using these products. WE DO NOT WARRANT THAT THE FOLLOWING INFORMATION IS COMPLETE, ACCURATE, OR UP-TO-DATE. OUR ONLY WARRANTY IS CONTAINED IN THE FORT'S SOFTWARE PROGRAM LICENSE AGREEMENT, DATED 10/88. 1-2-3 by Lotus Development Corp. Compatible with V-EMM Beware that 1-2-3 requires some conventional memory for every cell in your spreadsheet. Use the "Home" and "End Home" keys to locate the upper-left and lower-right corners of your spreadsheet. For most spreadsheets, the minimum amount of conventional memory required is approximately 4 bytes times the number of rows times the number of columns. This amount of conventional memory is required whether you are using V-EMM or an EMS board. When either expanded memory or conventional memory gets low, the MEM status indicator comes on. When either type of memory runs out, the Memory Full error is issued. If the range appears much larger than you expect, there may be an inconspicuous data item in the cell, or perhaps a "Range Format" may have been applied to the cell. If you cannot find the reason for an excessively large range, you might try "File Combine Copy Specified-Range" into a clear worksheet. Please note that several of the spreadsheets listed below have similar quirks regarding their use of conventional memory versus expanded memory. Please consult the spread- sheet vendor for more information. Symphony by Lotus Development Corp. Compatible with V-EMM Similar comments regarding conventional memory usage also apply to Symphony. SuperCalc by Computer Associates Compatible with V-EMM Excel by Microsoft Compatible with V-EMM Previous versions of V-EMM required that you instruct Excel not to use extended memory (via the "ExtendedMemory=0" parameter in the WIN.INI file). This version of V-EMM permits Excel to share extended memory with V-EMM. (See note on HIMEM.SYS.) Please note that Excel's use of extended memory is distinct from its use of expanded memory. Excel has always been able to use expanded memory provided by V-EMM. Surpass by Surpass Software Systems Compatible with V-EMM Quattro by Borland International Compatible with V-EMM Beware that Quattro requires some conventional memory for every cell in your spreadsheet. For most spreadsheets, the minimum amount of conventional memory required is approx- imately 4 bytes per cell. Framework by Ashton-Tate Compatible with V-EMM Silk by Daybreak Technologies Compatible with V-EMM Words & Figures by Lifetree Compatible with V-EMM Javelin by Javelin Software See below Javelin requires the "aliasing" feature, described below. When using VEMMSIM.SYS or VEMMSIME.SYS, Javelin is incompatible with V-EMM. When using VEMMSIM2.SYS or a real expanded memory mana- ger, Javelin is compatible with V-EMM. Smart by Innovative Software Compatible with V-EMM Smart expects the EMS Page Frame to be located in high memory. When using the VEMMSIM.SYS or VEMMSIME.SYS commands, DO NOT specify the S=0000 option. DESQview by Quarterdeck Office Systems Incompatible with V-EMM Windows/286 by Microsoft Compatible with V-EMM When using VEMMSIM.SYS or VEMMSIME.SYS, Windows will not exploit expanded memory for program or data storage. But EMS applications running under Windows (such as Excel or 1-2-3) can use expanded memory. (See notes on SMARTDRV.SYS and HIMEM.SYS.) Please note that Windows can exhibit this behavior when using an EMS board. If Windows doesn't like the location of the EMS Page Frame, it simply ignores expanded memory. Software Carousel by Softlogic Solutions Compatible with V-EMM The VEMMTSR1 program should be running. Taskview (Omniview) by Sunny Hill Software Compatible with V-EMM The VEMMTSR1 program should be running. HIMEM by Microsoft See below HIMEM.SYS is distributed by Microsoft through a number of channels. HIMEM version 2.04 (and below) contains a serious defect that renders it unusable with all other programs that use extended memory. If you have HIMEM, our technical support staff may be able to provide you with a patch to correct the problem. With our patch, HIMEM is compatible with V-EMM. The forthcoming HIMEM v2.05 is expected to incorporate this correction, and thus should be compatible with V-EMM. Reflex by Borland International Compatible with V-EMM Paradox by Ansa See below Paradox includes its own disk cache. This automatic disk- caching should be disabled via the Paradox Custom Configuration Program. SpeedStor by Storage Dimensions See below Disk Manager by Ontrack Computer Systems See below When these products are used to configure incompatible media, the V-EMM paging-file cannot be placed on such media. Other- wise, these products are compatible with V-EMM. RAMDRIVE.SYS by Microsoft Compatible with V-EMM RAMDRIVE is a RAM-disk program, provided with Microsoft Windows and with some versions of MS-DOS. RAMDRIVE can be installed in conventional memory, extended memory, or expanded memory and is compatible with V-EMM in all modes. For a RAM-disk in expanded memory, we recommend you use our VEMMDSK driver. SMARTDRV.SYS by Microsoft See below SMARTDRV is a disk-caching program, provided with Microsoft Windows. If possible, SMARTDRV should be configured to use a portion of extended memory. Otherwise, SMARTDRV should be configured to use conventional memory. In these cases, SMARTDRV is compatible with V-EMM. Lightning by PCSG See below Lightning prefers to use expanded memory for its disk- caching. You may choose to run V-EMM without the paging- file. Or you may "hide" V-EMM (via the VEMMHIDE command) while installing Lightning, in which case Lightning will use conventional memory for its cache buffers. In these cases, Lightning is compatible with V-EMM. Super PC-Kwik by Multisoft See below If possible, Super PC-Kwik should be configured to use a portion of extended memory. Otherwise, Super PC-Kwik should be configured to use conventional memory. In these cases, Super PC-Kwik is compatible with V-EMM. Ready! by Living Videotext Compatible with V-EMM The VEMMTSR1 program must be running. Turbo Lightning by Borland International Compatible with V-EMM The VEMMTSR1 program must be used if Turbo Lightning references any RAM-disk contained in expanded memory. Sidekick by Borland International Compatible with V-EMM The VEMMTSR1 program should be running. PrintQ by Software Directions Compatible with V-EMM The VEMMTSR1 program should be running. Personal REXX by Mansfield Software Group Compatible with V-EMM KEDIT by Mansfield Software Group Compatible with V-EMM AutoCAD by Autodesk Compatible with V-EMM Large memory requirements make AutoCAD difficult to install with VEMMSIM.SYS or VEMMSIME.SYS SAS by SAS Institute, Inc. See below SAS is compatible with V-EMM. However, SAS makes extensive use of expanded memory for swapping code. When SAS is used with VEMMSIM.SYS or VEMMSIME.SYS, performance is generally unaccept- able. When used with VEMMSIM2.SYS or with a real EMS board, performance is generally good. Word Perfect Libraries by Word Perfect Corp. Compatible with V-EMM Publisher's Paintbrush by Z-Soft Compatible with V-EMM Show Partner by Brightbill-Roberts Compatible with V-EMM Fontasy by ProSoft Compatible with V-EMM Extend-a-Name by World Software Compatible with V-EMM Non-Volatile RAM-Disk by Fort's Software Compatible with V-EMM PC-DOS 4.0 BUFFERS= Command by IBM Corp. See below PC-DOS 4.0 FASTOPEN Command by IBM Corp. See below PC-DOS 4.0 VDISK.SYS by IBM Corp. See below PC-DOS 4.0 includes limited support of expanded memory by these commands. Numerous bugs exist in IBM's support of expanded memory. Errors in handling the CONFIG.SYS BUFFERS= command, for example, can result in corruption of your hard-disk. DO NOT specify the /X option with any of these commands. Otherwise, these commands are compatible with V-EMM. PC-DOS 4.0 XMAEM.SYS by IBM Corp. See below PC-DOS 4.0 XMA2EMS.SYS by IBM Corp. See below These PC-DOS 4.0 Device Drivers can turn a few of IBM's memory boards into EMS boards. As such, these drivers can be used with V-EMM in the same way that an EMS board can be used with V-EMM. (V-EMM would be used with a paging-file to provide virtual memory.) If you DO NOT specify the P254 or P255 options on the XMA2EMS device driver, these drivers are compatible with V-EMM. Please note: These PC-DOS 4.0 EMS drivers are not in compli- ance with the EMS 4.0 specification. (They fail the PC Maga- zine Labs EMS 4.0 Performance Tests, for example.) But when these drivers are used together with V-EMM, the combination PASSES the PC Labs' EMS 4.0 test! F-EMM by Fort's Software Compatible with V-EMM F-EMM, the Fort's Software Expanded Memory Manager, provides true LIM EMS 4.0 support for many PS/2 Model 50 and 60 memory boards. The IBM Memory Expansion Option (6450344) and IBM's Expanded Memory Adapters (1497252 and 1497259) are supported. Several third-party boards are also supported. F-EMM can be used by itself to achieve 100% compatible LIM EMS 4.0 support on these boards. F-EMM can also be used with V-EMM in the same way that an EMS board can be used with V-EMM. (V-EMM would be used with a paging-file to provide virtual memory.) QEMM 50/60 by Quarterdeck Office Systems Compatible with V-EMM QEMM 50/60 is the Quarterdeck label version of F-EMM. It is licensed to Quarterdeck Office Systems by Fort's Software. QEMM 50/60 can also be used with V-EMM in the same way that an EMS board can be used with V-EMM. (V-EMM would be used with a paging-file to provide virtual memory.) QEMM 386 by Quarterdeck Office Systems Compatible with V-EMM QEMM 386 can be used with V-EMM in the same way that an EMS board can be used with V-EMM. (V-EMM would be used with a paging-file to provide virtual memory.) 386MAX by Qualitas Compatible with V-EMM 386MAX can be used with V-EMM in the same way that an EMS board can be used with V-EMM. (V-EMM would be used with a paging-file to provide virtual memory.) 386LOAD by Qualitas Compatible with V-EMM 386LOAD can be used to load the VEMM.SYS device driver in high memory. You should specify 386LOAD's SIZE=65520 parameter. The VEMM.SYS device driver needs this much storage for initialization only! The driver will terminate using a much smaller quantity of memory. TECHNICAL OVERVIEW OF SOURCES OF INCOMPATIBILITY ------------------------------------------------ In this section, we identify 5 major classes of potential incompatibilities. If you are using the listed driver (or option), you MAY have problems of the indicated class. If you are not using the listed driver, you WILL NOT have problems of the indicated class. NOTE: THE DESCRIPTIONS OF COMPATIBILITY PROBLEMS ARE FAIRLY TECHNICAL. THE NON-TECHNICAL READER IS ADVISED TO SKIP THIS SECTION. Classes of Drivers loaded / options used Potential Problems ----------------------------- ------------------ VEMMSIM.SYS A, M VEMMSIME.SYS A, E, M VEMM.SYS D= parameter D All uses of V-EMM B A - Aliasing is not supported in this configuration. B - The EMS "Busy" status can be reported to callers. D - A hard disk is used in this configuration. E - Extended memory is used in this configuration. M - A significant amount of memory is consumed in this configuration. CLASS A - Aliasing is not supported ----------------------------------- "Aliasing" is the ability to map the same piece of physical memory into two or more different locations in logical memory at the same time. We are aware of only one commercial product that relies upon "aliasing". CLASS B - The EMS "Busy" status can be reported to callers ---------------------------------------------------------- The EMS Specification says that an EMS driver can be called at any point in time. The driver should always be able to perform its work, regardless of what system activity is occurring. The ability to be called at any time is called "reentrancy". When a driver is entirely self-contained (writing directly to registers on its own board, for example), the reentrancy requirement can usually be met. EMS boards generally claim to meet this requirement. When the driver must utilize the services of DOS or of the BIOS, reentrancy can be achieved only if the underlying services are also reentrant. Neither PC DOS nor the BIOS are reentrant. Since V-EMM relies on the BIOS for access to extended memory and to the hard disk, V-EMM cannot guarantee reentrancy. Application programs generally pose no problem, since they would never present V-EMM with a reentrant call. Problems can occur if interrupt handlers, including pop-ups and print spoolers, attempt to access expanded memory. Such accesses can be an explicit call to the EMS or can be implicit (such as accessing a file contained in a RAM-disk, where the RAM-disk is implemented in expanded memory). Our program, VEMMTSR1, prevents most pop-ups and print spoolers (including the DOS PRINT command) from popping up when the EMS is busy. It does not prevent other interrupt handlers (such as DESQview's timer or keyboard interrupt handlers) from attempting to access EMS. Problems can also occur if the BIOS, itself, makes use of expanded memory. See the sections on incompatibility classes D and E for more information. CLASS D - A hard disk is used ----------------------------- To avoid many of reentrancy problems associated with problem class "B", above, V-EMM does not use DOS for paging to the hard disk. Instead, V-EMM accesses the disk through the BIOS. The first potential problem is that a few hard-disks do not provide a BIOS interface. Obviously, the V-EMM paging-file cannot be placed on such a disk. Even if you have no other hard-disk, V-EMM can still be used for EMS simulation with the VEMMSIME.SYS or VEMMSIM2.SYS device drivers. The second potential problem is that third-party disk-partitioning schemes sometimes produce unrecognizable media. if a disk was partitioned and formatted by the PC DOS FDISK and FORMAT commands, V-EMM will be able to use it. If use of standard PC DOS partitions is not possible, our technical support staff can frequently get V-EMM to recognize your disk. The third potential problem is if the BIOS, itself, makes use of expanded memory. This can occur only if a third-party product has hooked the BIOS hard-disk routines, thus making itself an extension of the BIOS. Problems then occur only if the third-party product uses expanded memory. Certain disk-caching programs are a classic example. While V-EMM is using the disk to hold EMS data, the disk-cache is using EMS to hold disk data. Each program calls the other to store the data. General- ly, your system will freeze-up. If the disk-caching program does not properly check return codes from V-EMM, the disk-caching program can (rarely) corrupt your hard-disk. There are several solutions to the disk-caching problems. First, configure the disk-cache to use extended memory, rather than expanded memory. If this is not possible, configure V-EMM to do without the paging-file. If this is not possible, disable caching of the drive on which the paging-file is located. And if this is not possible, consider another disk-caching program. If the disk-cache uses extended memory (such as IBMCACHE), or if the disk-cache works by intercepting DOS interrupts or by intercepting DOS device driver calls, the cache should be compatible with V-EMM. CLASS E - Extended memory is used --------------------------------- Use of extended memory by more than one program has always been a compatibility headache. Older programs that use extended memory tend to assume they have complete ownership of all extended memory. Some permit the user to specify which portion of extended memory is to be used. A few programs have looked for extended memory allocated in the style used by IBM's VDISK program. A few programs have tried to mimic the style used by IBM's VDISK program to reflect their own usage. Such techniques have been only moderately successful. (Consider for example, that two different versions of VDISK (e.g., the PC DOS 3.2 and 3.3 versions) cannot recognize each other's presence.) Using a technique introduced by IBM with their IBMCACHE program, VEMMSIME.SYS takes the specified amount of memory from the top of extended memory. It then hides the memory it consumes from programs loaded later than itself. This technique appears to be quite reliable, provided you can load the newer, smarter programs before the older, dumber programs. Another potential problem is if the BIOS, itself, makes use of expanded memory. This can occur only if a third-party product has hooked the BIOS Block Move routine, thus making itself an extension of the BIOS. Problems then occur only if the third-party product uses expanded memory. CLASS M - A significant amount of memory is consumed ---------------------------------------------------- Although not an incompatibility, per se, when V-EMM is used with the VEMMSIM.SYS or VEMMSIME.SYS device drivers, approximately 76 kilobytes of conventional memory is consumed. In exchange for that conventional memory, you get up to 32768 kilobytes of expanded memory. Programs with extremely large conventional memory requirements may not fit. When used in an environment where a large amount of memory is devoted to TSRs or device drivers (including many networking environments), programs with large conventional memory requirements may not fit. The VEMMHIDE command lets you hide (and reveal) expanded memory without rebooting. In many cases, when you "hide" expanded memory, we will temporarily yield 64 kilobytes of memory to DOS. Then when you "reveal" expanded memory, we will reclaim the memory from DOS.